Configuration As Code Security Vulnerabilities and Issues — Configuration As Code CVE List

Lucene search

JenkinsConfiguration As Code

5 matches found

CVE•added 2019/07/31 1:15 p.m.•65 views

CVE-2019-10343

Jenkins Configuration as Code Plugin 1.24 and earlier did not properly apply masking to values expected to be hidden when logging the configuration being applied.

3.3CVSS4.1AI score0.00015EPSS

CVE•added 2019/07/31 1:15 p.m.•62 views

CVE-2019-10362

Jenkins Configuration as Code Plugin 1.24 and earlier did not escape values resulting in variable interpolation during configuration import when exporting, allowing attackers with permission to change Jenkins system configuration to obtain the values of environment variables.

5.5CVSS5.4AI score0.00119EPSS

CVE•added 2019/07/31 1:15 p.m.•61 views

CVE-2019-10344

Missing permission checks in Jenkins Configuration as Code Plugin 1.24 and earlier in various HTTP endpoints allowed users with Overall/Read access to access the generated schema and documentation for this plugin containing detailed information about installed plugins.

4.3CVSS4.4AI score0.00031EPSS

CVE•added 2019/07/31 1:15 p.m.•61 views

CVE-2019-10345

Jenkins Configuration as Code Plugin 1.20 and earlier did not treat the proxy password as a secret to be masked when logging or encrypted for export.

5.5CVSS5.6AI score0.00011EPSS

CVE•added 2019/07/31 1:15 p.m.•55 views

CVE-2019-10363

Jenkins Configuration as Code Plugin 1.24 and earlier did not reliably identify sensitive values expected to be exported in their encrypted form.

4.9CVSS5.1AI score0.00066EPSS